A:

One solution is to use the AIL_set_file_callbacks function to point to your own routines for doing I/O. A better one for most applications is to take advantage of AIL_open_stream's ability to accept a system file handle (on Win32/Win64, see FileHndl.c for an example).

You can also use AIL_set_file_async_callbacks to point to your own routines for doing asynchronous I/O on certain platforms. Asynchronous streaming is used by default on MacOS 9, Wii and PS2 - the other platforms use synchronous IO from a background thread.

Most applications should allow Miles to manage its own file access. There are very few reasons to provide your own file-access callbacks to Miles... and with Miles's extensive use of multithreading, there are a lot of things that can go wrong if you do.